fix: Cascade overflow pre-effects to prevent bytecode encoding panic #306
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
emit_match_with_cascade()to split overflow pre-effects into epsilon chainWhy
Unlabeled alternations inject
Null + Seteffects for missing captures per branch. With 5+ branches, this exceeded the 3-bit limit (max 7) forpre_count, causing u16 overflow that corrupted successor addresses and panicked with "range start index 90816 out of range".The fix cascades overflow effects into leading epsilon transitions, matching the existing pattern for successor overflow.